home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01b.txt
/
000186_icon-group-sender_Wed Dec 5 16:29:07 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id fB5NSgU29961
for icon-group-addresses; Wed, 5 Dec 2001 16:28:42 -0700 (MST)
Message-Id: <200112052328.fB5NSgU29961@baskerville.CS.Arizona.EDU>
From: eka@corp.cirrus.com (Eka Laiman)
Subject: Re: Bio Informatics
To: trutkin@physics.clarku.edu (Taybin Rutkin)
Date: Wed, 5 Dec 2001 12:41:05 -0800 (PST)
Cc: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 748
> On Tue, 4 Dec 2001, Eka Laiman wrote:
> > As ICON is the direct descendant of SNOBOL, I see no reason why ICON
> > cannot do what PERL can - at least in the area of pattern matching.
Taybin Rutken wrote:
> I would be very interested in seeing a comparsion of Perl's regex
> capabilities and Icon's string scanning.
I believe that there is "regexp.icn" package in "library" package of
ICON which takes PERL regexp syntax and translates them into ICON and
execute the codes.
I think this provides the prove that ICON can do what PERL can.
The superiority of ICON's scanning mechanism is the ability to stop
the processing in the middle and resume the execution later. A very
important operation especially when we try to do "parsing".
-eka-